Ignore the request checksum when creating a delete marker - #6267
Ignore the request checksum when creating a delete marker #6267maeldonn wants to merge 2 commits into
Conversation
Hello maeldonn,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
A delete marker has no body, but createAndStoreObject took its checksum from the request headers, which on a multi-object delete cover the request XML. On an external location the mismatch failed the put, and the rollback error then hit an unguarded result.versionId in multiObjectDelete, killing the worker with a 502. Skip the header checksum for delete markers, and guard the result so any later error is returned as a proper S3 error. Issue: CLDSRV-984
0d7205f to
06ea87b
Compare
A delete marker has no body, but createAndStoreObject took its checksum
from the request headers, which on a multi-object delete cover the request
XML. On an external location the mismatch failed the put, and the rollback
error then hit an unguarded result.versionId in multiObjectDelete, killing
the worker with a 502. Skip the header checksum for delete markers, and
guard the result so any later error is returned as a proper S3 error.
Issue: CLDSRV-984